Problem

AndroidX Activity 1.9+ introduced a breaking change in the onNewIntent() method signature for Kotlin projects. The Android API changed to make the Intent parameter non-nullable (Intent instead of Intent?), which conflicts with the code automatically generated by our Expo plugin.

Technical context: This change in AndroidX Activity affects Expo projects starting from SDK 54, which adopted AndroidX Activity 1.9+. Projects using earlier versions (Expo SDK ≤ 53 with AndroidX Activity < 1.9) use the older nullable signature.

Before (AndroidX Activity < 1.9):

override fun onNewIntent(intent: Intent?) {
    super.onNewIntent(intent)
    Batch.onNewIntent(this, intent)
}

After (AndroidX Activity 1.9+):

override fun onNewIntent(intent: Intent) {  // Non-nullable!
    super.onNewIntent(intent)
    Batch.onNewIntent(this, intent)
}

Without this fix, developers using AndroidX Activity 1.9+ encounter Kotlin compilation errors when the plugin generates code with the old nullable signature.

Solution

Added the optional shouldUseNonNullableIntent parameter to the Expo plugin config, allowing developers to specify the Intent parameter nullability based on their AndroidX Activity version.

Usage Examples

For AndroidX Activity 1.9+:

{
  "plugins": [
    [
      "@batch.com/react-native-plugin",
      {
        "androidApiKey": "YOUR_ANDROID_API_KEY",
        "iosApiKey": "YOUR_IOS_API_KEY",
        "shouldUseNonNullableIntent": true
      }
    ]
  ]
}

For AndroidX Activity < 1.9 - default behavior:

{
  "plugins": [
    [
      "@batch.com/react-native-plugin",
      {
        "androidApiKey": "YOUR_ANDROID_API_KEY",
        "iosApiKey": "YOUR_IOS_API_KEY"
      }
    ]
  ]
}

Note: If shouldUseNonNullableIntent is not specified, it defaults to false to maintain backward compatibility with existing projects.